New Features
IG-435 Possibility to login to a dashboard once, and not needing to login in again even if restarting the device
To enhance productivity and reduce login-related frustrations, we've implemented refresh tokens. This eliminates the need for operators to log in every time they access the dashboard, even when using a shared tablet or PC. Users can now seamlessly access the dashboard without the hassle of repeated logins and password management. This implementation aligns with the industry-standard OAuth 2.0 protocol and enhances DCC's security and usability.
IG-541 Beta implementation of S7 write via remote access widget
This release introduces the ability to write selected values to a Siemens PLC. This functionality empowers users to modify PLC settings, adjust parameters directly from the DCC, eliminating the need for physical access to the PLC. Note that this feature is implemented as Beta in this release
IG-558 Support for generic MQTT devices based on the generic JSON MQTT format
A generic MQTT device type has been added to the list of supported MQTT devices. This device type uses the generic JSON data format for MQTT messages that is generated when creating the IoT device on the DCC, hence the the MQTT device must support a custom JSON format.
IG-640 Support for superscript text to Unit in data source
This release introduces the ability to add superscript text to units within the data source in the dashboard section, enhancing the clarity and comprehensiveness of the data representation
IG-685 Allow defining basic branding of platform when logged in
This release empowers admin users to easily customize basic graphics elements within the platform, enabling them to personalize the platform's visual identity and align it with their branding guidelines. This feature fosters a sense of ownership and reinforces the perception that the platform is fully integrated into their organization.
This option can be found under account setup -> company settings
Bug Fixes
IG-688 The default value for OPCUASecurityPolicy and OPCUAUserTokenType is not applied to the JSON-conf.
Resolved an issue where the default values for OPCUASecurityPolicy ("none") and OPCUAUserTokenType ("anonymous") were not being applied to the JSON configuration when adding an OPC-UA collector.
IG-690 In some scenarios strings could contain "dirty characters"
In some cases, random characters would be prefixed to the received string and typically displayed as unknown characters. This has been fixed. Note that the fix only applies for new fetched data, where as historic string data may still contain "dirty characters"
IG-721 Crash when opening Event notification tab on IoT Admin page when no Recipient group exists
With introduction of Event notifications and recipient groups, you could still define individual recipients for the machine without creating an Event notification group, but when selecting the Event notification tab in the IoT Admin, the page would crash. This has been fixed